Fix support for large RDF/XML parsing in AoT builds#221
Merged
Ostrzyciel merged 1 commit intomainfrom Sep 14, 2025
Merged
Conversation
Karolina-Bogacka
approved these changes
Sep 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #220
This took me a while to figure out. Unfortunately we cannot query the XML parsing limits directly, as that's considered JVM-internal, so we instead check the JVM version. If someone uses a different JVM that does not follow these limits... well, sorry, we have no way of checking that, really.
We set the higher limits through a barely documented (just Javadoc) API in Graal. This is also used by Quarkus, so it should be fine.
The new
jelly-cli voutput looks like: